Method for managing user information of application, device, and system

ABSTRACT

Example methods and apparatus for managing user information of an application are described. One example method is applied to a user management device of a cloud platform, where the cloud platform is configured to hear an application registered by a user with the cloud platform. The method includes receiving a user management registration request of a first application, where the first application is one of applications registered with the cloud platform, and the user management registration request of the first application carries an identifier of the first application. A user management instance is created for the first application according to the user management registration request and the identifier of the first application, where the user management instance is used to manage user information of the first application. The user management instance is invoked to process a service that is in the first application and related to the user information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/209,531, filed on Mar. 23, 2021, which is a continuation of U.S.patent application Ser. No. 15/837,483, filed on Dec. 11, 2017, now U.S.Pat. No. 10,986,166, which is a continuation of InternationalApplication No. PCT/CN2016/071332, filed on Jan. 19, 2016, which claimspriority to Chinese Patent Application No. 201510323682.4, filed on Jun.12, 2015. All of the afore-mentioned patent applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

The present invention relates to the field of computer technologies, andin particular, to a method for managing user information of anapplication, a device, and a system.

BACKGROUND

In the cloud computing era, a mode in which a server platform or adevelopment environment is provided for a user as a service is referredto as a platform-as-a-service (PaaS). Emergence of the PaaS mayaccelerate development of an application because the PaaS can provide amiddleware platform for an enterprise customized research anddevelopment and provide a database, an application server, and the like.The PaaS may increase a quantity of resources used. on a Web platform.Based on the PaaS platform, a user may quickly develop an applicationrequired by the user.

In the prior art, when an application developer develops an applicationbased on the PaaS platform, for an application that needs a usermanagement function, the developer needs to personally develop a usermanagement module, which is configured to implement the user managementfunction of the application. However, basic user management functionsrequired by applications are the same, including “user”, “role”,“permission”, “session”, and the like. Therefore, the user managementfunctions are repeatedly developed, which prolongs development periodsof the applications.

SUMMARY

Embodiments of the present invention provide a method for managing userinformation of an application, so that a problem in the prior art thatan application developer needs to repeatedly develop a user informationmanagement module of the application is resolved, and a developmentperiod of the application is shortened. The embodiments of the presentinvention further provide a corresponding apparatus and system.

A first aspect of the present invention provides a method for managinguser information of an application, where the method is applied to auser management device of a cloud platform, the cloud platform isconfigured to bear an application registered by a user with the cloudplatform, and the method includes:

receiving a user management registration request of a first application,where the first application is one of applications registered with thecloud platform, and the user management registration request of thefirst application carries an identifier of the first application;

creating a user management instance for the first application accordingto the user management registration request and the identifier of thefirst application, where the user management instance is used to manageuser information of the first application; and

invoking the user management instance to process a service that is inthe first application and related to the user information.

With reference to the first aspect, in a first possible implementationmanner, the creating a user management instance for the firstapplication according to the user management registration request andthe identifier of the first application includes:

generating a user management instance according to the user managementregistration request and a user management instance template; and

establishing a correspondence between the identifier of the firstapplication and the generated user management instance to obtain theuser management instance of the first application.

With reference to the first aspect or the first possible implementationmanner of the first aspect, in a second possible implementation manner,the invoking the user management instance to process a service that isin the first application and related to the user information includes:

invoking the user management instance to receive a user informationaccess request sent by user equipment that runs the first application,where the user information access request carries authenticationinformation; and

performing authentication according to the authentication information,after the authentication succeeds, obtaining, from a user informationdatabase maintained by the user management instance, user informationrequested by the first application, and returning, to the userequipment, the user information requested by the first application.

With reference to the first aspect or the first possible implementationmanner of the first aspect, in a third possible implementation manner,the invoking the user management instance to process a service that isin the first application and related to the user information includes:

invoking the user management instance to receive a user managementextension request sent by a network management device, where the usermanagement extension request carries extension information, and theextension information is functional information that is newly added forthe first application; and

establishing an association between the extension information and theuser information maintained by the user management instance, so that theuser management instance accesses the extension information, and sendingan extension success response message to the network management device.

With reference to the first aspect or the first possible implementationmanner of the first aspect, in a fourth possible implementation manner,the invoking the user management instance to process a service that isin the first application and related to the user information includes:

invoking the user management instance to receive an access request thatis of a second application and sent by a network management device,where the access request of the second application carriesauthentication information of the first application; and

performing authentication according to the authentication information,and after the authentication succeeds, providing the user information ofthe first application for the second application.

With reference to the fourth possible implementation manner of the firstaspect, in a fifth possible implementation manner, the providing theuser information of the first application for the second applicationincludes:

configuring authentication information of the second application for thesecond application, and sending the authentication information of thesecond application to the network management device, so that the networkmanagement device configures the authentication information of thesecond application for the second application, where the authenticationinformation of the second application is used when the secondapplication accesses the user management instance.

With reference to the first aspect and the first to the fifth possibleimplementation manners of the first aspect, in a sixth possibleimplementation manner, after the creating a user management instance forthe first application according to the user management registrationrequest and the identifier of the first application, the method furtherincludes:

invoking the user management instance to receive registration requestssent by different user equipment for registering the first application,where the registration requests for registering the first applicationcarry user information; and

creating a user information database and adding the user informationinto the database.

A second aspect of the present invention provides a user managementdevice, where the user management device is applied to a cloud platform,the cloud platform is configured to bear an application registered by auser with the cloud platform, and the user management device includes:

a receiving module, configured to receive a user management registrationrequest of a first application, where the first application is one ofapplications registered with the cloud platform, and the user managementregistration request of the first application carries an identifier ofthe first application;

a creating module, configured to create a user management instance forthe first application according to the user management registrationrequest received by the receiving module and the identifier of the firstapplication, where the user management instance is used to manage userinformation of the first application; and

an invoking module, configured to invoke the user management instance,which is created by the creating module, to process a service that is inthe first application and related to the user information.

With reference to the second aspect, in a first possible implementationmanner, the creating module includes:

a generating submodule, configured to generate a user managementinstance according to the user management registration request and auser management instance template; and

an establishing submodule, configured to establish a correspondencebetween the identifier of the first application and the generated usermanagement instance, which is generated by the generating submodule, toobtain the user management instance of the first application.

With reference to the second aspect or the first possible implementationmanner of the second aspect, in a second possible implementation manner,the user management instance includes: a first receiving submodule, afirst authentication submodule, a first obtaining submodule, and a firstsending submodule, where

the first receiving submodule is configured to: when being invoked bythe invoking module, receive a user information access request sent byuser equipment that runs the first application, where the userinformation access request carries authentication information;

the first authentication submodule is configured to: when being invokedby the invoking module, perform authentication according to theauthentication information received by the first receiving submodule;

the first obtaining submodule is configured to: when being invoked bythe invoking module, after the authentication performed by the firstauthentication submodule succeeds, obtain, from a user informationdatabase maintained by the user management instance, user informationrequested by the first application; and

the first sending submodule is configured to: when being invoked by theinvoking module, return, to the user equipment, the user informationthat is requested by the first application and obtained by the firstobtaining submodule.

With reference to the second aspect or the first possible implementationmanner of the second aspect, in a third possible implementation manner,the user management instance includes: a second receiving submodule, anassociation establishing submodule, and a second sending submodule,where

the second receiving submodule is configured to: when being invoked bythe invoking module, receive a user management extension request sent bya network management device, where the user management extension requestcarries extension information, and the extension information isfunctional information that is newly added for the first application;

the association establishing submodule is configured to: when beinginvoked by the invoking module, establish an association between theextension information and the user information maintained by the usermanagement instance, so that the user management instance accesses theextension information; and

the second sending submodule is configured to: when being invoked by theinvoking module, send an extension success response message to thenetwork management device after the association establishing submoduleestablishes the association.

With reference to the second aspect or the first possible implementationmanner of the second aspect, in a fourth possible implementation manner,the user management instance includes: a third receiving submodule, asecond authentication submodule, and an information providing submodule,where

the third receiving submodule is configured to: when being invoked bythe invoking module, receive an access request that is of a secondapplication and sent by a network management device, where the accessrequest of the second application carries authentication information ofthe first application;

the second authentication submodule is configured to: when being invokedby the invoking module, perform authentication according to theauthentication information received by the third receiving submodule;and

the information providing submodule is configured to provide the userinformation of the first application for the second application afterthe authentication performed by the second authentication submodulesucceeds.

With reference to the fourth possible implementation manner of thesecond aspect, in a fifth possible implementation manner, theinformation providing submodule includes a configuration submodule and athird sending submodule, where

the configuration submodule is configured to configure authenticationinformation of the second application for the second application whenbeing invoked by the invoking module; and

the third sending submodule is configured to: when being invoked by theinvoking module, send the authentication information of the secondapplication to the network management device, so that the networkmanagement device configures the authentication information of thesecond application for the second application, where the authenticationinformation of the second application is used when the secondapplication accesses the user management instance.

With reference to the second aspect and the first to the fifth possibleimplementation manners of the second aspect, in a sixth possibleimplementation manner,

the invoking module is further configured to invoke the user managementinstance to receive registration requests sent by different userequipment for registering the first application, where the registrationrequests for registering the first application carry user information;and

the creating module is further configured to create a user informationdatabase and add the user information into the database.

A third aspect of the present invention provides a cloud platform, wherethe cloud platform is configured to bear an application registered by auser with the cloud platform, the cloud platform includes a usermanagement device, and

the user management device is the user management device according tothe foregoing second aspect or any possible implementation manner of thesecond aspect.

According to the method that is for managing user information of anapplication and provided in the embodiments of the present invention, auser management instance may be created on a cloud platform for eachapplication in which user management needs to be performed, the usermanagement instance is invoked to process a service that is in theapplication and related to user information, and a developer does notneed to develop user information of the application. Compared with theprior art in which each application developer needs to personallydevelop a user management module, in the method that is for managinguser information of an application and provided in the embodiments ofthe present invention, a user management instance may be created foreach application that has a requirement, so as to manage userinformation of the application, so that repeated development for theuser information of the application may be avoided, and a developmentperiod of the application is shortened; in addition, for eachapplication, there may be a dedicated user management instance, so thatflexibility of user management is enhanced.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of the presentinvention more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showmerely some embodiments of the present invention, and a person ofordinary skill in the art may still derive other drawings from theseaccompanying drawings without creative efforts.

FIG. 1 is a schematic diagram of an embodiment of a cloud platformaccording to an embodiment of the present invention;

FIG. 2 is a schematic diagram of another embodiment of a cloud platformaccording to an embodiment of the present invention;

FIG. 3 is a schematic diagram of another embodiment of a cloud platformaccording to an embodiment of the present invention;

FIG. 4 is a schematic diagram of another embodiment of a cloud platformaccording to an embodiment of the present invention;

FIG. 5 is a schematic diagram of another embodiment of a cloud platformaccording to an embodiment of the present invention;

FIG. 6 is a schematic diagram of another embodiment of a cloud platformaccording to an embodiment of the present invention;

FIG. 7 is a schematic diagram of an embodiment of a method for managinguser information of an application according to an embodiment of thepresent invention;

FIG. 8 is a schematic diagram of an embodiment of a user managementdevice according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of another embodiment of a user managementdevice according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of another embodiment of a usermanagement device according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of another embodiment of a usermanagement device according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of another embodiment of a usermanagement device according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of another embodiment of a usermanagement device according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of another embodiment of a usermanagement device according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of another embodiment of a usermanagement device according to an embodiment of the present invention;and

FIG. 16 is a schematic diagram of an embodiment of a physical machinethat operates a user management device according to an embodiment of thepresent invention.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present invention provide a method for managing userinformation of an application, which may avoid repeated development ofthe user information of the application and shorten a development periodof the application; in addition, for each application, there may be adedicated user management instance, so that flexibility of usermanagement is enhanced. The embodiments of the present invention furtherprovide a corresponding apparatus and system. Details are described inthe following separately.

To make a person skilled in the art understand the technical solutionsin the present invention better, the following clearly describes thetechnical solutions in the embodiments of the present invention withreference to the accompanying drawings in the embodiments of the presentinvention. Apparently, the described embodiments are merely some but notall of the embodiments of the present invention. All other embodimentsobtained by a person of ordinary skill in the art based on theembodiments of the present invention without creative efforts shall fallwithin the protection scope of the present invention.

From a perspective of a hardware resource, a cloud platform provided inthe embodiments of the present invention may be a server cluster. Avirtual machine is configured on a server to implement bearing andmanagement of an application. Therefore, a user management device in theembodiments of the present invention may be a virtual machine on thecloud platform, or may certainly be an independent physical host.According to logical levels, the cloud platform may be divided into aninfrastructure as a service (IaaS) layer, a platform-as-a-service (PaaS)layer, and an application layer, which are commonly referred to as an Ilayer, a P layer, and an application layer. As shown in FIG. 1 , the Ilayer includes a physical resource and a virtualized resource. The Player includes a portal, an application development tool chain, anapplication running environment, application management, servicemanagement, a service repository, one-click deployment, and the like.The application layer includes multiple applications. FIG. 1 uses a bankapplication as an example, where the bank application includes anapplication that is newly deployed by a bank and an application that hasbeen deployed by the bank. The application that is newly deployed by thebank includes an Internet application, a mobile application, and bigdata analysis, and the application that has been deployed by the bankincludes an enterprise management application, an office application,and a counter application. Certainly, these applications are only usedas examples herein; actually, many other applications are furtherincluded. In addition, FIG. 1 only uses a bank system as an example fordescription, Actually, various applications may be deployed on the cloudplatform, and a corresponding management instance may be created on theP layer for management of each application. In multiple embodiments ofthe method for managing user information of an application according tothe present invention, a process of managing the user information of theapplication is separately described.

As shown in FIG. 2 , an embodiment of the method for managing userinformation of an application according to an embodiment of the presentinvention includes:

In this embodiment of the present invention, multiple applications maybe registered with a PaaS. For an application that has a user managementrequirement, a user management device may create a user managementinstance for each application that has a user management requirement.For example, in FIG. 2 , an application 1, an application 3, and anapplication 5 each has its own user management instance. Creation of theuser management instance may be triggered by an application developer.For example, the developer triggers a user management registrationrequest of the application 1 by using a network management device, wherethe user management registration request carries an identifier of theapplication, so that the user management device may create the usermanagement instance of the application 1 for the application 1 accordingto the user management registration request and the identifier of theapplication 1, and the user management instance of the application 1 isconfigured to manage user information of the application 1. For aservice that is of the application 1 and related to the userinformation, the user management device may invoke the user managementinstance of the application Ito process the service.

In this way, compared with the prior art in which each applicationdeveloper needs to personally develop a user management module, in themethod that is for managing user information of an application andprovided in this embodiment of the present invention, a user managementinstance may be created for each application that has a requirement, soas to manage user information of the application, so that repeateddevelopment for the user information of the application may be avoided,and a development period of the application is shortened; in addition,for each application, there may be a dedicated user management instance,so that flexibility of user management is enhanced.

As shown in FIG. 3 , the user management instance of the application 1is used as an example, and each user management instance may have thefollowing modules: a user management message processing module, a userrelationship logic management module, an application access permissionmanagement module, a user management extension module, and a databasemodule. The following is description of functions of these modules.

The user management message processing module is configured to receiveand process a message, and forward the message to another module in theuser management instance.

The user relationship logic management module is configured to implementa most basic user management function, including logic management ofinformation such as “user”, “role”, “permission”, and “session”, and isresponsible for interacting with a database.

The application access permission management module is configured toauthenticate whether an application that uses the user information haspermission for access, so as to protect security of the userinformation.

The user management extension module extends a user managementcapability by adjusting a user logical relationship and the database.

The database is configured to store the user information.

An APP1, an APP3, and an APP5 may be understood as APP clients installedin user equipment.

As shown in FIG. 4 , an embodiment of the method for managing userinformation of an application according to this embodiment includes:

101. A user management message processing module receives a userinformation access request of an APP1, where the user information accessrequest carries authentication information.

The APP1 may be a client installed in user equipment. The authenticationinformation may be an identifier of an APP, or may be an authenticationkey of an APP.

102. The user management message processing module sends the userinformation access request to an application access permissionmanagement module.

103. The application access permission management module performsapplication access authentication on the APP1, and after theauthentication of the APP1 succeeds, the application access permissionmanagement module returns an application authentication success responsemessage to the user management message processing module.

104. After obtaining the authentication success response message, theuser management message processing module sends a user informationrequest to a user relationship logic management module.

105. The user relationship logic management module queries a databasefor user information according to requested content.

106. The database returns corresponding user information.

107. The user relationship logic management module sorts userinformation data and returns user information required by the App1 tothe user management message processing module.

108. The user management message processing module returns the userinformation to the App1.

A scenario of this embodiment of the present invention may be a scenarioof logging in to an APP, such as game login. When a game player logs into a game in user equipment, after an account and a password areentered, the user equipment sends a user information access request to auser management instance of the game, where the user information accessrequest may carry an identifier of the APP, or may carry anauthentication key of the APP. The application access permissionmanagement module performs access authentication according to theidentifier or the authentication key of the APP. After theauthentication succeeds, the user relationship logic management modulequeries a database for user information of the game APP. After anaccount and a password of the game APP are obtained from the database byquery, the user relationship logic management module performs matchingbetween the password obtained from the database and the account and thepassword that are sent by the user equipment. After the matchingsucceeds, the user management message processing module may return alogin success response message to the user equipment.

As shown in FIG. 5 , another embodiment of the method for managing userinformation of an application according to this embodiment includes:

This embodiment of the present invention describes a scenario in whichuser management logic is extended according to an actual need of a user.

After a user management instance is created, a developer may extend usermanagement according to a requirement of the application. For example, aWeb application needs to customize a display effect of a page for eachuser, and configuration information related to the display effect of theuser needs to be added into a user management database.

201. A developer sends a user management extension request to a usermanagement message processing module by using a network managementdevice, where the user management extension request carriesauthentication information and extension information.

For example, the user management extension request may be a request foradding a user information table, where key information such as entrycontent of the information table that needs to be added and accesspermission information obtained when an instance is created are carriedin the request.

202. The user management message processing module sends anauthentication information to an access permission management module toperform access authentication of the application. The application accesspermission management module performs access authentication according tothe authentication information. After the authentication succeeds, anauthentication success message is returned to the user managementmessage processing module.

203. The user management message processing module sends a usermanagement extension request to a user management extension module, andafter obtaining an authentication success message, the user managementmessage processing module sends, to the user management extensionmodule, extension information that needs to be added.

For example, an information entry that needs to be added is sent to theuser management extension module.

204. The user management extension module sends a user managementextension command to a user relationship logic management module,transforms the extension information in the user management extensioncommand, and provides the transformed extension information to the userrelationship logic management module.

205. The user relationship logic management module adjusts andestablishes a user information relationship, and sends a userinformation table creation request to the database.

206. After successfully storing a user information entry, the databasereturns a creation success request.

207. The user relationship logic management module returns a userrelationship establishment success response to the user managementextension module.

208. The user management extension module returns a user informationextension success message to the user management message processingmodule.

209. The user management message processing module sends a userinformation extension success response to a network management device,and a subsequent application may directly use an added information entryto query a corresponding user information table.

As shown in FIG. 6 , another embodiment of the method for managing userinformation of an application according to this embodiment includes:

Content mainly described in this embodiment is a scenario of how tosupport different applications to share, by using a user managementservice, information related to a user.

An advantage of sharing user information is that for applications of asame developer, a user group can be quickly built for a new application.

301. A network management device sends an access request of an APP2 to auser management message processing module, where the access request ofthe APP2 carries authentication information of an APP1.

302. An application access permission management module performsauthentication according to the authentication information of the APP1,and after the authentication succeeds, configures authenticationinformation of the APP2 for the APP2.

Authentication is performed according to the authentication information,and after the authentication succeeds, the authentication information ofthe second application is configured for the second applicationaccording to the access request of the second application, and theauthentication information of the second application is sent to thenetwork management device, where the authentication information of thesecond application is used for the second application to use userinformation maintained by a user management instance of the firstapplication.

303. The network management device notifies the APP2 of key informationneeded for accessing a user management instance of the APP1, andtherefore the APP2 can use the user management instance of the APP1.

304. The APP2 accesses the user management instance of the APP1 by usingthe key information needed for accessing the user management instance ofthe APP1.

Referring to FIG. 7 , an embodiment of the method for managing userinformation of an application according to an embodiment of the presentinvention includes:

401. A user management device receives a user management registrationrequest of a first application, where the first application is one ofapplications registered with a cloud platform, the user managementregistration request of the first application carries an identifier ofthe first application, the user management device belongs to the cloudplatform, and the cloud platform is configured to bear an applicationregistered by a user with the cloud platform.

402. The user management device creates a user management instance forthe first application according to the user management registrationrequest and the identifier of the first application, where the usermanagement instance is used to manage user information of the firstapplication.

403. The user management device invokes the user management instance toprocess a service that is in the first application and related to theuser information.

The method that is for managing user information of an application andprovided in this embodiment of the present invention is applied to auser management device of a cloud platform, where the cloud platform isconfigured to bear an application registered by a user with the cloudplatform. The method includes: receiving a user management registrationrequest of a first application, where the first application is one ofapplications registered with the cloud platform, and the user managementregistration request of the first application carries an identifier ofthe first application; creating a user management instance for the firstapplication according to the user management registration request andthe identifier of the first application, where the user managementinstance is used to manage user information of the first application;and invoking the user management instance to process a service that isin the first application and related to the user information. Comparedwith the prior art in which each application developer needs topersonally develop a user management module, in the method that is formanaging user information of an application and provided in thisembodiment of the present invention, a user management instance may becreated for each application that has a requirement, so as to manageuser information of the application, so that repeated development forthe user information of the application may be avoided, and adevelopment period of the application is shortened; in addition, foreach application, there may be a dedicated user management instance, sothat flexibility of user management is enhanced.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 7 , in a first optional embodiment of the method that is formanaging user information of an application and provided in anembodiment of the present invention, the creating a user managementinstance for the first application according to the user managementregistration request and the identifier of the first application mayinclude:

generating a user management instance according to the user managementregistration request and a user management instance template; and

establishing a correspondence between the identifier of the firstapplication and the generated user management instance to obtain theuser management instance of the first application.

In this embodiment of the present invention, creating a user managementinstance according to a user management instance template accelerates aspeed of creating a user management entity.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 7 or the first optional embodiment, in a second optional embodimentof the method that is for managing user information of an applicationand provided in an embodiment of the present invention,

the invoking the user management instance to process a service that isin the first application and related. to the user information mayinclude:

invoking the user management instance to receive a user informationaccess request sent by user equipment that runs the first application,where the user information access request carries authenticationinformation; and

performing authentication according to the authentication information,after the authentication succeeds, obtaining, from a user informationdatabase maintained by the user management instance, user informationrequested by the first application, and returning, to the userequipment, the user information requested by the first application.

This embodiment of the present invention may be understood withreference to description of FIG. 4 , and no detailed description isgiven herein.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 7 or the first optional embodiment, in a third optional embodimentof the method that is for managing user information of an applicationand provided in an embodiment of the present invention, the invoking theuser management instance to process a service that is in the firstapplication and related to the user information may include:

invoking the user management instance to receive a user managementextension request sent by a network management device, where the usermanagement extension request carries extension information, and theextension information is functional information that is newly added forthe first application; and

establishing. an association between the extension information and theuser information maintained by the user management instance, so that theuser management instance accesses the extension information, and sendingan extension success response message to the network management device.

This embodiment of the present invention may be understood withreference to description of FIG. 5 , and no detailed description isgiven herein.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 7 or the first optional embodiment, in a fourth optional embodimentof the method that is for managing user information of an applicationand provided in an embodiment of the present invention, the invoking theuser management instance to process a service that is in the firstapplication and related to the user information may include:

invoking the user management instance to receive an access request thatis of a second application and sent by a network management device,where the access request of the second application carriesauthentication information of the first application, and

performing authentication according to the authentication information,and after the authentication succeeds, providing the user information ofthe first application for the second application.

Optionally, on the basis of the foregoing fourth optional embodimentcorresponding to FIG. 7 , in a fifth optional embodiment of the methodthat is for managing user information of an application and provided inan embodiment of the present invention, the providing the userinformation of the first application for the second application mayinclude:

configuring authentication information of the second application for thesecond application, and sending the authentication information of thesecond application to the network management device, so that the networkmanagement device configures the authentication information of thesecond application for the second application, where the authenticationinformation of the second application is used when the secondapplication accesses the user management instance.

The fourth and the fifth optional embodiments of the present inventionmay be understood with reference to description of FIG. 6 , and nodetailed description is given herein.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 7 or any one of the optional embodiments, in a sixth optionalembodiment of the method that is for managing user information of anapplication and provided in an embodiment of the present invention,after the creating a user management instance for the first applicationaccording to the user management registration request and the identifierof the first application, the method may further include:

invoking the user management instance to receive registration requestssent by different user equipment for registering the first application,where the registration requests for registering the first applicationcarry user information; and

creating a user information database and adding the user informationinto the database.

In this embodiment of the present invention, user information may begradually added into the database when each user performs registration.

Referring to FIG. 8 , in an embodiment of a user management device 50provided in an embodiment of the present invention, the user managementdevice 50 is applied to a cloud platform, where the cloud platform isconfigured to bear an application registered by a user with the cloudplatform, and the user management device 50 includes:

a receiving module 501, configured to receive a user managementregistration request of a first application, where the first applicationis one of applications registered with the cloud platform, and the usermanagement registration request of the first application carries anidentifier of the first application;

a creating module 502, configured to create a user management instance503 for the first application according to the user managementregistration request received by the receiving module 501 and theidentifier of the first application, where the user management instanceof the first application is configured to manage user information of thefirst application; and

an invoking module 504, configured to invoke the user managementinstance 503, which is created by the creating module 502, to process aservice that is in the first application and related to the userinformation.

The user management device provided in this embodiment of the presentinvention is applied to a cloud platform, where the cloud platform isconfigured to bear an application registered by a user with the cloudplatform. The user management device 50 includes: a receiving module501, which receives a user management registration request of a firstapplication, where the first application is one of applicationsregistered with the cloud platform, and the user management registrationrequest of the first application carries an identifier of the firstapplication; a creating module 502, which creates a user managementinstance 503 for the first application according to the user managementregistration request received by the receiving module 501 and theidentifier of the first application, where the user management instance503 of the first application is configured to manage user information ofthe first application; and an invoking module 504, which invokes theuser management instance 503, which is created by the creating module502, to process a service that is in the first application and relatedto the user information. Compared with the prior art in which eachapplication developer needs to personally develop a user managementmodule, according to the user management device provided in thisembodiment of the present invention, a user management instance may becreated for each application that has a requirement, so that userinformation of the application is managed, repeated development for theuser information of the application may be avoided, and a developmentperiod of the application is shortened; in addition, for eachapplication, there may be a dedicated user management instance, so thatflexibility of user management is enhanced.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 8 , referring to FIG. 9 , in a first optional embodiment of theuser management device 50 provided in an embodiment of the presentinvention, the creating module 502 includes:

a generating submodule 5021, configured to generate a user managementinstance according to the user management registration request and auser management instance template; and

an establishing submodule 5022, configured to establish a correspondencebetween the identifier of the first application and the generated usermanagement instance, which is generated by the generating submodule, toobtain the user management instance of the first application.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 8 , referring to FIG. 10 , in a second optional embodiment of theuser management device 50 provided in an embodiment of the presentinvention, the user management instance 503 includes: a first receivingsubmodule 5031, a first authentication submodule 5032, a first obtainingsubmodule 5033, and a first sending submodule 5034.

The first receiving submodule 5031 is configured to: when being invokedby the invoking module 504, receive a user information access requestthat is of the first application and sent by user equipment that runsthe first application, where the user information access request carriesauthentication information.

The first authentication submodule 5032 is configured to: when beinginvoked by the invoking module 504, perform authentication according tothe authentication information received by the first receiving submodule5031.

The first obtaining submodule 5033 is configured to: when being invokedby the invoking module 504, after the authentication performed by thefirst authentication submodule 5032 succeeds, obtain, from a userinformation database maintained by the user management instance of thefirst application, user information requested by the first application.

The first sending submodule 5034 is configured to: when being invoked bythe invoking module 504, return, to the user equipment, the userinformation that is requested by the first application and obtained bythe first obtaining submodule 5033.

This embodiment of the present invention may be understood withreference to description of FIG. 4 . Though names of modules aredifferent, functions are actually the same, and no detailed descriptionis given herein.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 8 , referring to FIG. 11 , in a third optional embodiment of theuser management device 50 provided in an embodiment of the presentinvention, the user management instance 503 includes: a second receivingsubmodule 5035, an association establishing submodule 5037, and a secondsending submodule 5038.

The second receiving submodule 5035 is configured to: when being invokedby the invoking module 504, receive a user management extension requestsent by a network management device, where the user management extensionrequest carries extension information, and the extension information isfunctional information that is newly added for the first application.

The association establishing submodule 5037 is configured to: when beinginvoked by the invoking module 504, establish an association between theextension information and the user information maintained by the usermanagement instance, so that the user management instance accesses theextension information.

The second sending submodule 5038 is configured to: when being invokedby the invoking module 504, send an extension success response messageto the network management device after the association establishingsubmodule 5037 establishes the association.

This embodiment of the present invention may be understood withreference to description of FIG. 5 . Though names of modules aredifferent, functions are actually the same, and no detailed descriptionis given herein.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 8 , referring to FIG. 12 , in a fourth optional embodiment of theuser management device 50 provided in an embodiment of the presentinvention, the user management instance 503 includes: a third receivingsubmodule 50391, a second authentication submodule 50392, and aninformation providing submodule 50393.

The third receiving submodule 50391 is configured to: when being invokedby the invoking module 504, receive an access request that is of asecond application and sent by a network management device, where theaccess request of the second application carries authenticationinformation of the first application.

The second authentication submodule 50392 is configured to: when beinginvoked by the invoking module 504, perform authentication according tothe authentication information received by the third receiving submodule50391.

The information providing submodule 50393 is configured to provide theuser information of the first application for the second applicationafter the authentication performed by the second authenticationsubmodule 50392 succeeds.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 12 , referring to FIG. 13 , in a fifth optional embodiment of theuser management device 50 provided in an embodiment of the presentinvention, the information providing submodule 50393 includes: aconfiguration submodule 503931 and a third sending submodule 503932.

The configuration submodule 503931 is configured to configureauthentication information of the second application for the secondapplication when being invoked by the invoking module 504.

The third sending submodule 503932 is configured to: when being invokedby the invoking module 504, send the authentication information of thesecond application to the network management device, so that the networkmanagement device configures the authentication information of thesecond application for the second application, where the authenticationinformation of the second application is used when the secondapplication accesses the user management instance.

This embodiment of the present invention may be understood withreference to description of FIG. 6 . Though names of modules aredifferent, functions are actually the same, and no detailed descriptionis given herein.

Optionally, on the basis of the foregoing embodiment corresponding toFIG. 8 or any one of optional embodiments corresponding to FIG. 9 toFIG. 13 , in a fourth optional embodiment of the user management device50 provided in an embodiment of the present invention,

the invoking module 504 is further configured to invoke the usermanagement instance to receive registration requests sent by differentuser equipment for registering the first application, where theregistration requests for registering the first application carry userinformation; and

the creating module 502 is further configured to create a userinformation database and add the user information into the database.

In this embodiment of the present invention, the first receivingsubmodule, the second receiving submodule, the third receivingsubmodule, the first sending submodule, the second sending submodule,and the third sending submodule may be the user management messageprocessing module in the embodiments corresponding to FIG. 2 to FIG. 6 ;the first authentication submodule and the second authenticationsubmodule may be the application access permission management module inthe embodiments corresponding to FIG. 2 to FIG. 6 ; the first obtainingsubmodule may be the user relationship logic management module in theembodiments corresponding to FIG. 2 to FIG. 6 ; and the associationestablishing submodule may be the user management extension module inthe embodiments corresponding to FIG. 2 to FIG. 6 .

In multiple embodiments of the foregoing user management device, itshould be understood that, in one implementation manner, a receivingmodule, a receiving submodule, and a sending submodule may beimplemented by an input/output I/O device (such as a network adapter),and a creating module, an invoking module, an authentication submodule,an association establishing submodule, and a configuration submodule maybe implemented by a processor by executing a program or an instructionin a memory (in other words, the creating module, the invoking module,the authentication submodule, the association establishing submodule,and the configuration submodule are implemented by means of mutualcooperation between the processor and a special instruction in a memorycoupled with the processor); in another implementation manner, areceiving module, a receiving submodule, and a sending submodule may beimplemented by an input/output I/O device (such as a network adapter),and a creating module, an invoking module, an authentication submodule,an association establishing submodule, and a configuration submodule maybe separately implemented by using a dedicated circuit, where for aspecific implementation manner, refer to the prior art, and details arenot described herein again; in still another implementation manner, areceiving module, a receiving submodule, and a sending submodule may beimplemented by an input/output I/O device (such as a network adapter),and a creating module, an invoking module, an authentication submodule,an association establishing submodule, and a configuration submodule maybe implemented by a field-programmable gate array (FPGA,Field-Programmable Gate Array), where for a specific implementationmanner, refer to the prior art, and details are not described hereinagain. The present invention includes but is not limited to theforegoing implementation manners, and it should be understood that allsolutions implemented according to the idea of the present inventionshall fall within the protection scope of the embodiments of the presentinvention.

This embodiment provides a hardware structure of a user managementdevice. Referring to FIG. 14 , the hardware structure of the usermanagement device may include:

three parts: a transceiving component, a software component, and ahardware component.

The transceiving component is a hardware circuit that is configured tocomplete packet transceiving.

The hardware component may also be referred to as a “hardware processingmodule”, or may be more simply referred to as “hardware” for short. Thehardware component mainly includes a hardware circuit that implements(probably with cooperation from another auxiliary component such as amemory) some specific functions on the basis of dedicated hardwarecircuits such as an FPGA and an ASIC. Generally, a processing speed ofthe hardware component is much faster than that of a general purposeprocessor. However, a function of the hardware component is hard tochange once being customized, and therefore, it is not flexible toimplement a function, and the hardware component is generally configuredto process some fixed functions. It should be noted that, in an actualapplication, the hardware component may also include processors such asan MCU (a microprocessor, such as a single-chip microcomputer) or a CPU.However, a main function of these processors is not to completeprocessing of big data but to perform some control. In such anapplication scenario, a system form by these components is a hardwarecomponent.

The software component (or simply referred to as “software”) mainlyincludes a general purpose processor (such as a CPU) and some auxiliarycomponents (such as storage devices like a memory and a hard disk). Theprocessor may be provided with a corresponding processing function bymeans of programming. When being implemented by using software, afunction may be flexibly configured according to a service requirement,but a speed of the function is slower than that of the hardwarecomponent. After data is processed by the software, the hardwarecomponent may send processed data by using the transceiving component,or may send the processed data to the transceiving component by using aninterface connected to the transceiving component.

In this embodiment, the transceiving component is configured to receivea request in the foregoing embodiment, and the software component or thehardware component is configured to create a user management instanceand the like.

Other functions of the hardware component and the software component aredescribed in detail in the foregoing embodiment, and details are notdescribed herein again.

With reference to the accompany drawings, the following gives detaileddescription of a solution in which a receiving submodule and a sendingsubmodule may be implemented by an input/output I/O device (such as anetwork adapter), and a creating module, an invoking module, anauthentication submodule, an association establishing submodule, and aconfiguration submodule may be implemented by a processor by executing aprogram or an instruction in a memory.

FIG. 15 is a schematic structural diagram of a user management device 50according to an embodiment of the present invention. The user managementdevice 50 is applied to a cloud platform, where the cloud platform isconfigured to bear an application registered by a user with the cloudplatform. The user management device 50 includes a processor 510, amemory 550, and an input/output I/O device 530, where the memory 550 mayinclude a read-only memory and a random access memory, and provide anoperation instruction and data for the processor 510. A part of thememory 550 may further include a non-volatile random access memory(NVRAM).

In some implementation manners, the memory 550 stores the followingelements: executable modules or data structures, or their subsets, ortheir extended sets.

In this embodiment of the present invention, the operation instructionstored in the memory 550 (the operation instruction may be stored in anoperating system) is invoked to:

receive a user management registration request of a first application,where the first application is one of applications registered with thecloud platform, and the user management registration request of thefirst application carries an identifier of the first application;

create a user management instance for the first application according tothe user management registration request and the identifier of the firstapplication, where the user management instance is used to manage userinformation of the first application; and

invoke the user management instance of the first application to processa service that is in the first application and related to the userinformation.

It can be seen that, compared with the prior art in which eachapplication developer needs to personally develop a user managementmodule, according to the user management device provided in thisembodiment of the present invention, a user management instance may becreated for each application that has a requirement, so as to manageuser information of the application, so that repeated development forthe user information of the application may be avoided, and adevelopment period of the application is shortened; in addition, foreach application, there may be a dedicated user management instance, sothat flexibility of user management is enhanced.

The processor 510 controls an operation of the user management device50, and the processor 510 may also be referred to as a CPU (CentralProcessing Unit, central processing unit). The memory 550 may include aread-only memory and a random access memory, and provide an instructionand data for the processor 510. A part of the memory 550 may furtherinclude a non-volatile random access memory (NVRAM). In a specificapplication, all components of the user management device 50 are coupledtogether by using a bus system 520, where the bus system 520 may furtherinclude a power bus, a control bus, a status signal bus, and the like inaddition to a data bus. However, for clear description, various types ofbuses are marked as the bus system 520 in the figure.

The methods disclosed in the foregoing embodiments of the presentinvention may be applied to the processor 510, or implemented by theprocessor 510. The processor 510 may be an integrated circuit chip andhas a signal processing capability. In an implementation process, thesteps in the foregoing methods may be completed by means of anintegrated logic circuit of hardware in the processor 510 or aninstruction in a form of software. The foregoing processor 510 may be ageneral purpose processor, a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), a field programmablegate array (FPGA) or another programmable logic component, a discretegate or a transistor logic component, or a discrete hardware component,and may implement or execute methods, steps and logical block diagramsdisclosed in the embodiments of the present invention. The generalpurpose processor may be a microprocessor, or the processor may be anyconventional processor or the like. Steps of the methods disclosed. withreference to the embodiments of the present invention may be directlyexecuted and completed by means of a hardware decoding processor, or maybe executed and completed by using a combination of hardware andsoftware modules in a decoding processor. A software module may belocated in a mature storage medium in the art, such as a random accessmemory, a flash memory, a read-only memory, a programmable read-onlymemory, an electrically erasable programmable memory, or a register. Thestorage medium is located in the memory 550, and the processor 510 readsinformation in the memory 550 and completes the steps in the foregoingmethods in combination with hardware of the processor.

Optionally, the processor 510 is specifically configured to generate auser management instance according to the user management registrationrequest and a user management instance template, and establish acorrespondence between the identifier of the first application and thegenerated user management instance to obtain the user managementinstance of the first application.

Optionally, the processor 510 is specifically configured to: invoke theuser management instance to receive a user information access requestsent by user equipment that runs the first application, where the userinformation access request carries authentication information; performauthentication according to the authentication information; after theauthentication succeeds, obtain, from a user information databasemaintained by the user management instance, user information requestedby the first application; and return, to the user equipment, the userinformation requested by the first application.

Optionally, the processor 510 is specifically configured to: invoke theuser management instance to receive a user management extension requestsent by a network management device. where the user management extensionrequest carries extension information, and the extension information isfunctional information that is newly added for the first application;establish an association between the extension information and the userinformation maintained by the user management instance, so that the usermanagement instance accesses the extension information; and send anextension success response message to the network management device.

Optionally, the processor 510 is specifically configured to: invoke theuser management instance to receive an access request that is of asecond application and sent by a network management device, where theaccess request of the second application carries authenticationinformation of the first application, perform authentication accordingto the authentication information, and provide the user information ofthe first application for the second application after theauthentication succeeds.

Optionally, the processor 510 is specifically configured to configureauthentication information of the second application for the secondapplication, and send the authentication information of the secondapplication to the network management device, so that the networkmanagement device configures the authentication information of thesecond application for the second application, where the authenticationinformation of the second application is used when the secondapplication accesses the user management instance.

Optionally, the processor 510 is further configured to invoke the usermanagement instance to receive registration requests sent by differentuser equipment for registering the first application, where theregistration requests for registering the first application carry userinformation, create a user information database, and add the userinformation into the database.

It should be noted that the user management device provided in thisembodiment of the present invention may be specifically a cloud host ona cloud platform, where the cloud host may be a virtual machine runningon a physical machine. As shown in FIG. 16 , a physical machine 1200includes a hardware layer 100, a VMM (Virtual Machine Monitor, virtualmachine monitor) 110 running above the hardware layer 100, and a hostHost 1201 and several virtual machines (VM, Virtual Machine) that arerunning above the VMM 110, where the hardware layer includes but is notlimited to an I/O device, a CPU, and a memory. The user managementdevice on the cloud platform according to this embodiment of the presentinvention may be specifically a virtual machine in the physical machine1200, for example, a VM 1202. One or more cloud applications are runningon the VM 1202, where each cloud application, such as a databaseapplication or a map application, is used to implement a correspondingservice function, and these applications may be developed by a developerand then deployed in a cloud computing system. In addition, the VM 1202further runs an executable program, By running the executable programand using the host Host 1201 in a process of running the program, the VM1202 invokes a hardware resource of the hardware layer 100 to implementfunctions of a creating module, an invoking module, an authenticationsubmodule, an association establishing submodule, a configurationsubmodule of the user management device on the cloud platform.Specifically, the creating module, the invoking module, theauthentication submodule, the association establishing submodule, andthe configuration submodule may be included in the foregoing executableprogram in a form of a software module or a function, for example, theexecutable program may include: the creating module, the invokingmodule, the authentication submodule, the association establishingsubmodule, and the configuration submodule. The VM 1202 invokesresources such as a CPU and a Memory that are on the hardware layer 100to run the executable program, so as to implement the functions of thecreating module, the invoking module, the authentication submodule, theassociation establishing submodule, and the configuration submodule.

The embodiment corresponding to FIG. 15 and another optional embodimentmay be understood with reference to description of FIG. 1 to FIG. 13 ,and no detailed description is given herein.

A person of ordinary skill in the art may understand that all or some ofthe steps of the methods in the embodiments may be implemented by aprogram instructing relevant hardware (such as a processor). The programmay be stored in a computer-readable storage medium. The storage mediummay include: a ROM, a RAM, a magnetic disk, an optical disc, or thelike.

The foregoing gives detailed description on the method for managing userinformation of an application, the device, and the system that areprovided in the embodiments of the present invention. In thisspecification, specific examples are used to describe the principle andimplementation manners of the present invention, and the description ofthe embodiments is only intended to help understand the method and coreidea of the present invention. Meanwhile, a person of ordinary skill inthe art may, based on the idea of the present invention, makemodifications with respect to the specific implementation manners andthe application scope. Therefore, the content of this specificationshall not be construed as a limitation to the present invention.

What is claimed is:
 1. A method for managing user information of anapplication on a cloud platform, wherein the method comprises:receiving, by the cloud platform, a user management registration requestof a first application, wherein the user management registration requestof the first application carries an identifier of the first application;creating, by the cloud platform, a user management instance for managinguser information of the first application according to the usermanagement registration request; invoking, by the cloud platform, theuser management instance to process a service based on the userinformation of the first application.
 2. The method according to claim1, wherein processing the service based on the user information of thefirst application comprises: receiving an access request of a secondapplication, wherein the access request of the second applicationcarries authentication information of the first application; performingauthentication according to the authentication information carried inthe access request of the second application; and after theauthentication succeeds, providing the user information of the firstapplication for the second application.
 3. The method according to claim1, wherein the creating, by the cloud platform, the user managementinstance for managing user information of the first applicationaccording to the user management registration request and a usermanagement instance template comprises: generating the user managementinstance according to the user management registration request and theuser management instance template; and establishing a correspondencebetween the identifier of the first application and the generated usermanagement instance to obtain the user management instance of the firstapplication.
 4. The method according to claim 1, wherein the invoking,by the cloud platform, the user management instance to process a servicebased on the user information of the first application comprises:invoking the user management instance to receive a user informationaccess request sent by user equipment that runs the first application,wherein the user information access request carries authenticationinformation; performing authentication according to the authenticationinformation; after the authentication succeeds, obtaining, from a userinformation database maintained by the user management instance, userinformation requested by the first application; and returning the userinformation requested by the first application.
 5. The method accordingto claim 1, wherein the invoking, by the cloud platform, the usermanagement instance to process a service based on the user informationof the first application comprises: invoking the user managementinstance to receive a user management extension request sent by anetwork management device, wherein the user management extension requestcarries extension information, and wherein the extension information isfunctional information that is newly added for the first application;establishing an association between the extension information and theuser information maintained by the user management instance, wherein theuser management instance accesses the extension information; and sendingan extension success response message to the network management device.6. The method according to claim 2, wherein the providing the userinformation of the first application for the second applicationcomprises: configuring authentication information of the secondapplication for the second application; and sending the authenticationinformation of the second application to a network management device,wherein the network management device configures the authenticationinformation of the second application for the second application, andwherein the authentication information of the second application is usedwhen the second application accesses the user management instance. 7.The method according to a claim 1, the method further comprises:invoking, by the cloud platform, the user management instance to receiveregistration requests sent by different user equipment for registeringthe first application, wherein the registration requests for registeringthe first application carry user information; and creating a userinformation database and adding the user information into the userinformation database.
 8. A user management device, comprising: at leastone processor; and one or more memories coupled to the at least oneprocessor and storing instructions for execution by the at least oneprocessor to: receive a user management registration request of a firstapplication, wherein the user management registration request of thefirst application carries an identifier of the first application; createa user management instance for managing user information of the firstapplication according to the received user management registrationrequest; invoke the user management instance to process a service basedon the user information of the first application, wherein processing theservice based on the user information of the first applicationcomprises: receiving an access request that is of a second application,wherein the access request of the second application carriesauthentication information of the first application; performingauthentication according to the received authentication information; andproviding the user information of the first application for the secondapplication after the performed authentication succeeds.
 9. The usermanagement device according to claim 8, wherein processing the servicebased on the user information of the first application comprises:receiving an access request that is of a second application, wherein theaccess request of the second application carries authenticationinformation of the first application; performing authenticationaccording to the received authentication information; and providing theuser information of the first application for the second applicationafter the performed authentication succeeds
 10. The user managementdevice according to claim 8, wherein the one or more memories store theinstructions for execution by the at least one processor further to:generate the user management instance according to the user managementregistration request and a user management instance template; andestablish a correspondence between the identifier of the firstapplication and the generated user management instance to obtain theuser management instance of the first application.
 11. The usermanagement device according to claim 8, wherein the one or more memoriesstore the instructions for execution by the at least one processorfurther to: receive a user information access request sent by userequipment that runs the first application, wherein the user informationaccess request carries authentication information; performauthentication according to the received authentication information;after performed authentication succeeds, obtain, from a user informationdatabase maintained by the user management instance, user informationrequested by the first application; and return the user information thatis requested by the first application.
 12. The user management deviceaccording to claim 8, wherein the one or more memories store theinstructions for execution by the at least one processor to: receive auser management extension request sent by a network management device,wherein the user management extension request carries extensioninformation, and wherein the extension information is functionalinformation that is newly added for the first application; establish anassociation between the extension information and the user informationmaintained by the user management instance, wherein the user managementinstance accesses the extension information; and send an extensionsuccess response message to the network management device.
 13. The usermanagement device according to claim 12, wherein the one or morememories store the instructions for execution by the at least oneprocessor to: configure authentication information of the secondapplication for the second application; and send the authenticationinformation of the second application to the network management device,wherein the network management device configures the authenticationinformation of the second application for the second application, andwherein the authentication information of the second application is usedwhen the second application accesses the user management instance. 14.The user management device according to claim 8, wherein the one or morememories store the instructions for execution by the at least oneprocessor to: receive registration requests sent by different userequipment for registering the first application, wherein theregistration requests for registering the first application carry userinformation; and create a user information database and add the userinformation into the user information database.